This can happen if a deployment was staged and later cleaned up. Though
just as a helper when debugging issues, let's explicitly mention that
case.
Closes: #1841
Approved by: cgwalters
* service when a staged deployment is created.
*/
if (!self->staged_deployment)
- return TRUE;
+ {
+ ot_journal_print (LOG_INFO, "No deployment staged for finalization");
+ return TRUE;
+ }
/* Notice we send this *after* the trivial `return TRUE` above; this msg implies we've
* committed to finalizing the deployment. */